This chapter describes Token Ring Network Interface (TKR) messages. For information on message content and how to use the message, refer to the Introduction.
| TKR.001 |
Level: U-INFO
Short Syntax: TKR.001 unexp type frm LLC_control fm source_MAC ssap source_SAP dsap dest_SAP nt network ID
Long Syntax: TKR.001 Unexpected type frame LLC_control from source_MAC, ssap source_SAP, dsap dest_SAP, net network ID
Description: This message is generated when an unexpected 802.2 LLC frame type is received. Type may be I (information transfer) or S (supervisory). The frame was addressed to the router.
Cause: Host attempting to make 802.2 type 2 connection to router.
| TKR.002 |
Level: P-TRACE
Short Syntax: TKR.002 unexp type brd frm LLC_control fm source_MAC ssap source_SAP dsap dest_SAP nt network ID
Long Syntax: TKR.002 Unexpected type broadcast frame LLC_control from source_MAC, ssap source_SAP, dsap dest_SAP, net network ID
Description: This message is generated when an unexpected 802.2 LLC frame type is received. Type may be I (information transfer) or S (supervisory). The frame was a broadcast.
Cause: Host attempting to make 802.2 type 2 connection to router.
| TKR.003 |
Level: U-INFO
Short Syntax: TKR.003 unkn SNAP mfr cd number fm source_MAC nt network ID
Long Syntax: TKR.003 Unknown SNAP manufacturer code number from source_MAC net network ID
Description: This message is generated when a frame with an unknown organization code (not 000000) in the SNAP header is received. The frame was addressed to the router.
Cause: Host sending packets for unknown proprietary protocol using SNAP.
| TKR.004 |
Level: P-TRACE
Short Syntax: TKR.004 unkn SNAP mfr code number fm source_MAC nt network ID
Long Syntax: TKR.004 Unknown SNAP manufacturer code number from source_MAC net network ID
Description: This message is generated when a frame with an unknown organization code (not 000000) in the SNAP header is received. The frame was a broadcast.
Cause: Host sending packets for unknown proprietary protocol using SNAP.
| TKR.005 |
Level: U-INFO
Short Syntax: TKR.005 unkn SNAP type type_code fm source_MAC nt network ID
Long Syntax: TKR.005 Unknown SNAP type type_code from source_MAC net network ID
Description: This message is generated when a frame with an unknown SNAP type (within organization code 000000) is received. The frame was addressed to the router.
Cause: Host sending packets for unknown Ethernet type using SNAP.
| TKR.006 |
Level: P-TRACE
Short Syntax: TKR.006 unkn SNAP type type_code fm source_MAC nt network ID
Long Syntax: TKR.006 Unknown SNAP type type_code from source_MAC net network ID
Description: This message is generated when a frame with an unknown SNAP type (within organization code 000000) is received. The frame was a broadcast.
Cause: Host sending packets for unknown Ethernet type using SNAP.
| TKR.007 |
Level: U-INFO
Short Syntax: TKR.007 unkn SAP sap_number fm source_MAC nt network ID
Long Syntax: TKR.007 Unknown SAP sap_number from source_MAC net network ID
Description: This message is generated when a frame with an unknown destination SAP is received. The message was addressed to the router.
Cause: Host sending packets for unknown protocol identifier (SAP).
| TKR.008 |
Level: U-INFO
Short Syntax: TKR.008 unkn SAP sap_number fm source_MAC nt network ID
Long Syntax: TKR.008 Unknown SAP sap_number from source_MAC net network ID
Description: This message is generated when a frame with an unknown destination SAP is received. The message was a broadcast.
Cause: Host sending packets for unknown protocol identifier (SAP).
| TKR.009 |
Level: U-INFO
Short Syntax: TKR.009 unexp U frm LLC_control fm source_MAC ssap source_SAP dsap dest_SAP nt network ID
Long Syntax: TKR.009 Unexpected U frame LLC_control from source_MAC, ssap source_SAP, dsap dest_SAP, net network ID
Description: This message is generated when an unexpected 802.2 LLC U (unnumbered) frame type is received. (Only UI, XID, and TEST are supported.) The frame was addressed to the router.
| TKR.010 |
Level: P-TRACE
Short Syntax: TKR.010 unexp U frm LLC_control fm source_MAC ssap source_SAP dsap dest_SAP nt network ID
Long Syntax: TKR.010 Unexpected U frame LLC_control from source_MAC, ssap source_SAP, dsap dest_SAP, net network ID
Description: This message is generated when an unexpected 802.2 LLC U (unnumbered) frame type is received. (Only UI, XID, and TEST are supported.) The frame was a broadcast.
| TKR.014 |
Level: UI-ERROR
Short Syntax: TKR.014 selftest_phase fld error_condition nt network
Long Syntax: TKR.014 selftest_phase failed: error_condition, network network
Description: The self-test for the 802.5 Token-Ring card has reported an error during self-test. The phases are "Initial test", "Board reset", "Configuration", "Open", "Open: Lobe media test", "Open: Physical insertion", "Open: Address verification", "Open: Roll call poll", "Open: Request parameters", "Packet output", and "Packet receive". See message TKR-45 for IBM Token-Ring self-test failures.
Cause: In the "Initial test" phase, the error is "Buffer unavail". This indicates that there is a severe packet buffer shortage in the router.
Action: Increase memory size, or decrease size of routing tables.
Cause: In the "Board reset" phase, the error can be one of: "Initial test error", "Adaptor ROM CRC error", "Adaptor RAM error", "Instruction Test error", "Context/Interrupt Test error", "Protocol Handler Hardware Err", or "System Interface Register Err". Any of these indicate internal problems within the adapter chipset.
Action: Probable hardware failure of interface. Replace.
Cause: In the "Configuration" phase, the error can be one of: "Invalid init block", "Invalid options", "Invalid receive burst", "Invalid transmit burst", "Invalid DMA abort threshhold", "Invalid SCB", "Invalid SSB", "DIO Parity", "DMA timeout", "DMA parity", "DMA bus error", "DMA data error", or "Adaptor check". These can indicate a hardware problem within the chipset, or a software problem.
Action: Probable hardware failure of interface. Replace.
Cause: In the "Open" phase, the error can be one of: "Node address error", "List size error", "Buffer size error", "Expansion RAM error", "Transmit buffer count", or "Inavlid open option". These can indicate a hardware problem within the chipset, or a software problem.
Action: Probable hardware failure of interface. Replace.
Cause: In the "Open: Lobe media test", "Open: Physical insertion", "Open: Address verification", "Open: Participation in ring poll", and "Open: Request initialization" phases, the error can be one of: "Function failure", "Signal loss", "Timeout", "Ring failure", "Ring beaconing", "Duplicate node Address", "Request initialization", "Remove received", or "IMPL force received". These are indications of failures in the process of the MAC algorithms for joining the ring. The problem is probably in the ring or the cabling, not the interface.
Action: Investigate network problems in 802.5 ring that the interface is attempting to connect to.
Cause: In the "Packet output" phase, the error is "Unknown". The self-test packet that was sent by the node to itself did not have the address recognized bit set upon the completion of transmission.
Action: Investigate network problems, possible hardware problem.
Cause: In the "Packet input" phase, the error is "Unkown". The self-test packet that was sent by the node to itself was not received within half a second.
Action: Investigate network problems, possible hardware problem.
| TKR.015 |
Level: UI-ERROR
Short Syntax: TKR.015 dwn sts cls nt network
Long Syntax: TKR.015 Down, ring status close indication, network network
Description: The interface has automatically removed itself form the ring due to some serious error condition. This may be one of "Lobe wire fault", "Auto-removal error", or "Remove received". The interface will attempt to join the ring again, and may come up again.
Cause: There is a hardware problem with the ring or the interface. The exact cause is not logged, but these errors are counted, and the counters in the +interface command should indicate what the problem is.
Action: Look at the interface counters. "Lobe wire fault" indicates a problem with the network. "Auto-removal error" indicates internal problems with the interface. "Remove received" indicates that a network management station has instructed this station to leave the ring.
| TKR.016 |
Level: UI-ERROR
Short Syntax: TKR.016 dwn adap chk adapter_check_code nt network
Long Syntax: TKR.016 Down, adapter check adapter_check_code, network network
Description: The interface has been brought down because of an adaptor status check. The interface will not be self-tested, and will not come back up automatically. The adapter_check_code indicates which error occurred.
Cause: The adapter has detected a severe unrecoverable internal failure.
Action: If the problem persists, have the interface replaced.
| TKR.017 |
Level: UI-ERROR
Short Syntax: TKR.017 pkt sz configured_size too big for 4 Mbps, limting to maximum_size, nt network
Long Syntax: TKR.017 Packet size configured_size too big for 4 Megabit/Second, limiting to maximum_size, network network
Description: The user has set the packet size for the 802.5 network larger than is allowed for a 4 Megabit/second network. The 8144, 11407, and 17800 byte sizes are only legal on a 16 Megabit/second network.
| TKR.019 |
Level: UE-ERROR
Short Syntax: TKR.019 runt pkt ( length) frm source_address, net network
Long Syntax: TKR.019 runt packet ( length bytes) from node source_address, network network
Description: A packet has been received which is too short to contain the MAC and LLC headers.
Cause: External error.
| TKR.020 |
Level: UE-ERROR
Short Syntax: TKR.020 DN bd ln actual_length claimed_length source_MAC_address -> destination_MAC_address nt network
Long Syntax: TKR.020 DECnet packet received with a bad length actual actual_length claimed claimed_length from source_MAC_address to destination_MAC_address network network
Description: A DECnet packet was received with a length field that was larger than the actual length of the packet.
| TKR.021 |
Level: P-TRACE
Short Syntax: TKR.021 LOOP rcv source_MAC_address -> destination_MAC_address, nt network
Long Syntax: TKR.021 Loopback Protocol frame received from source_MAC_address to destination_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet was received.
| TKR.022 |
Level: UE-ERROR
Short Syntax: TKR.022 LOOP odd skp count, source_MAC_address -> destination_MAC_address, nt network
Long Syntax: TKR.022 Loopback Protocol, odd skipCount count from source_MAC_address to destination_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet had an odd skipCount in the packet. It will be discarded.
Cause: Programming error on remote node.
| TKR.023 |
Level: UE-ERROR
Short Syntax: TKR.023 LOOP bd skp count, source_MAC_address -> destination_MAC_address, nt network
Long Syntax: TKR.023 Loopback Protocol, bad skipCount count from source_MAC_address to destination_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet had a skipCount in the packet that points to beyond the end of the packet. It will be discarded.
Cause: Programming error on remote node.
| TKR.024 |
Level: P-TRACE
Short Syntax: TKR.024 LOOP func function not forw, source_MAC_address -> destination_MAC_address, nt network
Long Syntax: TKR.024 Loopback Protocol, function function not Forward Data from source_MAC_address to destination_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet did not have a function code of forward (2). It will be discarded.
Cause: Function code was reply (1), because we were the ultimate destination of this packet.
Action: None.
| TKR.025 |
Level: UE-ERROR
Short Syntax: TKR.025 LOOP mc fwd dst forward_MAC_address, source_MAC_address -> destination_MAC_address, nt network
Long Syntax: TKR.025 Loopback Protocol, multicast forward address forward_MAC_address from source_MAC_address to destination_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet has a forward address that is a multicast. It will be discarded.
Cause: Programming error in remote node.
| TKR.026 |
Level: P-TRACE
Short Syntax: TKR.026 LOOP fwd source_MAC_address -> forward_MAC_address, nt network
Long Syntax: TKR.026 Loopback Protocol, forwarding from source_MAC_address to forward_MAC_address, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet is being forwarded to the specified next hop.
| TKR.027 |
Level: UI-ERROR
Short Syntax: TKR.027 LOOP fwd to forward_Ethernet_address dsc, rsn code, nt network
Long Syntax: TKR.027 Loopback protocol, forward to forward_Ethernet_address discarded, for reason code, network network
Description: An Ethernet Loopback Protocol (Configuration Testing Protocol) packet could not be forwarded to the specified address, for the reason specified by code.
| TKR.028 |
Level: UI-ERROR
Short Syntax: TKR.028 rif table corruption for nt network
Long Syntax: TKR.028 rif related functions failed because of rif table corruption on network network
Description: The rif table is corrupted.
| TKR.029 |
Level: P_TRACE
Short Syntax: TKR.029 rif entry is being removed entry hardware_address protocol_type nt network
Long Syntax: TKR.029 rif aging function is removing entry hardware_address protocol_type network network
Description: The rif entry aging function is removing an entry from the rif table.
| TKR.030 |
Level: UI_ERROR
Short Syntax: TKR.030 MAC frm typ mac_frametype unex from hardware_address nt network
Long Syntax: TKR.030 MAC frame type mac_frametype unexpected from hardware_address network network
Description: The handler received a frame with an unexpected frame type.
| TKR.031 |
Level: P_TRACE
Short Syntax: TKR.031 Main rcd on nt network
Long Syntax: TKR.031 Maintenance packet received on net network
Description: The handler received a maintenance packet.
| TKR.032 |
Level: P_TRACE
Short Syntax: TKR.032 test frm mac_address, src sap source_sap, nt network
Long Syntax: TKR.032 test packet from mac_address, source sap source_sap, net network
Description: The handler received a test message.
| TKR.033 |
Level: P_TRACE
Short Syntax: TKR.033 xid frm mac_address, sap source_sap, nt network
Long Syntax: TKR.033 xid packet received from mac_address, source sap source_sap, net network
Description: The handler received an xid message.
| TKR.035 |
Level: U-TRACE
Short Syntax: TKR.035 new RIF ( RIF) for MAC_address nt network ID
Long Syntax: TKR.035 new RIF ( RIF) for MAC_address net network ID
Description: This message is generated when a new RIF is added to the 802.5 MAC address to RIF translation cache.
| TKR.036 |
Level: ALWAYS
Short Syntax: TKR.036 can't set 2nd grp addr MAC_address
Long Syntax: TKR.036 can't set 2nd group address MAC_address
Description: The Token-Ring hardware can only support one group address. A second address is being attempted to be installed.
| TKR.037 |
Level: ALWAYS
Short Syntax: TKR.037 Net network ID, Unkn SRT Cmd Completion code - SRT_Completion. Being restarted
Long Syntax: TKR.037 Network network ID, Has Received an Unknown SRT Command Completion code - SRT_Completion. Interface being restarted
Description: The Token-Ring board has returned an unexpected SRT Completion Code. This will cause the interface to enter self-test.
| TKR.038 |
Level: ALWAYS
Short Syntax: TKR.038 Net network ID, Cmnd to TKR failed - invld param(s). Being restarted
Long Syntax: TKR.038 Network network ID, Command to Token Ring Adapter failed - invalid parameter(s). Interface being restarted
Description: The Token-Ring board has returned an a illegal parameter status code indicating that one or more of the parameters passed to it were invalid. This will cause the interface to re-initialize.
| TKR.039 |
Level: ALWAYS
Short Syntax: TKR.039 Net network ID, Unkn TKR Cmd Completion code - Completion_Code. Being restarted
Long Syntax: TKR.039 Network network ID, Unknown Command Completion code - Completion_Code. Interface being restarted
Description: The Token-Ring board has returned an unexpected Completion Code. This will cause the interface to re-initialize.
| TKR.040 |
Level: ALWAYS
Short Syntax: TKR.040 Net network ID, Invld Command Command rcvd in tm_ioctl. Being restarted
Long Syntax: TKR.040 Network network ID,Invalid Command Command received by tm_ioctl from handler. Interface being restarted
Description: The tm_ioctl routine has received an invalid command from the device handler. This will cause the interface to re-initialize.
| TKR.041 |
Level: ALWAYS
Short Syntax: TKR.041 Net network ID, Invld Interrupt rcvd Interrupt from TKR adapter. Being restarted
Long Syntax: TKR.041 Network network ID, Invalid Interrupt Interrupt received from the TKR adapter. Interface being restarted
Description: The interrupt service routine has received an invalid interrupt from the adapter card. This will cause the interface to re-initialize.
| TKR.043 |
Level: UE-ERROR
Short Syntax: TKR.043 drop IPX pkt w/ encap_seen encaps - using encap_used encaps on int intnum
Long Syntax: TKR.043 dropped IPX pkt with encaps encap_seen using encap_used on interface intnum
Description: This message is generated when an IPX packet is recieved with an encapsulation other than that which has been selected for this interface
Cause: Normal for networks using multiple encapsulations on a single wire.
Action: None needed.
| TKR.044 |
Level: UE-ERROR
Short Syntax: TKR.044 odd RIF len frm MAC_address; pkt drpd nt network ID
Long Syntax: TKR.044 odd RIF length from MAC_address; packet dropped on net network ID
Description: The length byte in the RIF header was odd, which is illegal. The packet was dropped.
| TKR.045 |
Level: UI-ERROR
Short Syntax: TKR.045 selftest_phase fld error_condition nt network
Long Syntax: TKR.045 selftest_phase failed: error_condition, network network
Description: The self-test for the IBM 802.5 Token-Ring has reported an error during self-test. This message can often serve as a useful quick primitive diagnostic tool for the Token-Ring hardware. The phases are "reset", "load loader (part 1)", "load loader (part 2)", "download microcode", "check downloaded microcode", "Configuration", "Read interesting pointers", "open: lobe media test", "open: physical insertion", "open: address verification", "open: participation in ring poll", "open: request initialization", "Set bridge params", "Set STE wanted", "Packet output", "Packet receive", "SRT Config", "Set func/group address", "Unknown Test".
Cause: open: lobe media test: function failure.
Action: This is a basic cable problem. Check the cable. Check that router configuration has the correct media cable setting, that is, UTP or STP.
Cause: open: physical insertion fld ring beaconing. The Token-Ring is beaconing. This is usually due to one station having a misconfigured speed.
Action: Check that router configuration has the correct speed setting, that is, 4 Mbps or 16 Mbps. Check that all the stations in your ring are set to the same speed. Check for physical breaks in the Token-Ring.
Cause: open: address verification fld duplicate node address. The MAC address for this interface is a duplicate on the ring.
Action: Check that router configuration has the correct MAC address for this interface. Verify the other stations on your ring for a duplicate address.
Cause: Any of the "reset", "load loader (part 1)", "load loader (part 2)", "download microcode", "check downloaded microcode" phases.
Action: Probable hardware failure of interface. Replace.
Cause: In the "Configuration" phase, the error can be one of: "initial test error", "microcode crc error", "adapter ram error", "instruction test error", "context/interrupt test error", "protocol handler hardware err", "system interface register err", "invalid parameter length", "invalid options", "invalid receive burst", "invalid transmit burst", "invalid dma abort threshhold", "invalid dma test address", "dio parity", "dma timeout", "dma parity", "dma bus error", "dma data error", "adapter check".
Action: These are the failures from the diagnostics run by the adapter. Probable hardware failure of interface. Replace if it persists.
Cause: In the "Open" phase, the error can be one of: "Node address error", "List size error", "Buffer size error", "Expansion RAM error", "Transmit buffer count error", or "Inavlid open option".
Action: Probable hardware failure of interface. Replace.
Cause: The "open: lobe media test", "open: physical insertion", "open: address verification", "open: participation in ring poll", "open: request initialization" phases. The open operation has failed.
Action: These are fixable a lot of the time. The usual failures have already been described above. Check cable configuration and speed again. Investigate network or cabling problems, possible hardware problem.
Cause: Phases "Set bridge params", "Set STE wanted", "SRT Config", "Set func/group address" are phases related to setting the token-ring for bridging, group address, functional addresses, etc.
Action: This is more likely to be a software problem since the Token-Ring is already up and running successfully.
Cause: Packet output fld unknown. The Token-Ring driver could not send a test packet. This is more likely to be a software problem, such as the buffers within the router are exhausted.
Action: Restart router if it persists.
Cause: Packet receive fld unknown. The Token-Ring driver was unable to send a test packet around the ring and receive it.
Action: Check for an unusally large amount of traffic on the ring.
| TKR.046 |
Level: C-INFO
Short Syntax: TKR.046 FasTR frm drpd from SRC_address to Dest_address, RIF RIF, nt network
Long Syntax: TKR.046 Fast Token Ring Frame dropped from SRC_address to Dest_address, RIF RIF, net network
Description: A Fast Token Ring frame with a RIF was dropped.
| TKR.047 |
Level: C-INFO
Short Syntax: TKR.047 FasTR frm drpd from SRC_address to Dest_address, nt network
Long Syntax: TKR.047 Fast Token Ring frame dropped from SRC_address to Dest_address, net network
Description: A Fast Token Ring frame without a RIF was dropped.
| TKR.048 |
Level: C-INFO
Short Syntax: TKR.048 FasTR tst frm looped from SRC_address to Dest_address, nt network UP
Long Syntax: TKR.048 Fast Token Ring frame looped from SRC_address to Dest_address, net network
Description: A Fast Token Ring Test frame was looped back while the net was up.
| TKR.049 |
Level: C-INFO
Short Syntax: TKR.049 FasTR tst frm looped from SRC_address to Dest_address, nt network not UP
Long Syntax: TKR.049 Fast Token Ring frame looped from SRC_address to Dest_address, net network
Description: A Fast Token Ring Test frame was looped back while the net was not up.
| TKR.050 |
Level: C-INFO
Short Syntax: TKR.050 flash_condition flash state: flash_state, nt network
Long Syntax: TKR.050 flash_condition, flash state = flash_state network network
Description: Information notification for the Token Ring flash update process. The reasons are "Microcode update terminated after 3 attempts", "Non-AMD flash update is not supported", "Good status from flash update", "Error status from flash update", "Flash update is in progress".
| Panic tkrMacTooManyReg |
Short Syntax: tkr_regMacAddrUpCall: too many registered
Description: Internal problem.
Cause: Software bug.
Action: Inform customer service.
| Panic tkrMacStsTooManyReg |
Short Syntax: tkr_regStatusUpCall: too many registered
Description: Internal problem.
Cause: Software bug.
Action: Inform customer service.
| Panic tkrMacXmitTooManyReg |
Short Syntax: tkr_regXmitpCall: too many registered
Description: Internal problem.
Cause: Software bug.
Action: Inform customer service.